A new demo modelling tool that facilitates model transformations

The age of digitization requires rapid design and re-design of enterprises. Rapid changes can be realized using conceptual modelling. The design and engineering methodology for organizations (DEMO) is an established modelling method for representing the organization domain of an enterprise. However, heterogeneity in enterprise design stakeholders generally demand for transformations between conceptual modelling languages. Specifically, in the case of DEMO, a transformation into business process modelling and notation (BPMN) models is desirable to account to both, the semantic sound foundation of the DEMO models, and the wide adoption of the de-facto industry standard BPMN. Model transformation can only be efficiently applied if tool support is available. Our research starts with a state-of-the-art analysis, comparing existing DEMO modelling tools. Using a design science research approach, our main contribution is the development of a DEMO modelling tool on the ADOxx platform. One of the main features of our tool is that it addresses stakeholder heterogeneity by enabling transformation of a DEMO organization construction diagram (OCD) into a BPMN collaboration diagram. A demonstration case shows the feasibility of our newly developed tool.http://www.springer.com/series/7911hj2021Industrial and Systems Engineerin

From Expert Discipline to Common Practice: A Vision and Research Agenda for Extending the Reach of Enterprise Modeling

The benefits of enterprise modeling (EM) and its contribution to organizational tasks are largely undisputed in business and information systems engineering. EM as a discipline has been around for several decades but is typically performed by a limited number of people in organizations with an affinity to modeling. What is captured in models is only a fragment of what ought to be captured. Thus, this research note argues that EM is far from its maximum potential. Many people develop some kind of model in their local practice without thinking about it consciously. Exploiting the potential of this “grass roots modeling” could lead to groundbreaking innovations. The aim is to investigate integration of the established practices of modeling with local practices of creating and using model-like artifacts of relevance for the overall organization. The paper develops a vision for extending the reach of EM, identifies research areas contributing to the vision and proposes elements of a future research Agenda

Towards Enterprise-Grade Tool Support for DEMO

Part 2:Enterprise Modeling and Enterprise ArchitectureInternational audienceThe Design and Engineering Methodology for Organizations (DEMO) method is a core method within the discipline of Enterprise Engineering (EE). It enables the creation of so-called essential models of Organizations, which are enterprise models focusing on the organizational essence of an organization, primarily in terms of the actor roles involved, and the business transactions between these actor roles. The DEMO method has a firm theoretical foundation. At the same time, there is an increasing uptake of DEMO in practice.With the increased uptake of DEMO also comes a growing need for enterprise-grade tool support. In this paper, we therefore report on a study concerning the selection, configuration, and extension, of an enterprise-grade tool platform to support the use of DEMO in practice.The selection process resulted in the selection of Sparx Enterprise Architect for further experimentation in terms of configuration towards DEMO. The configuration of this tool framework to support DEMO modelling, also provided feedback on the consistency and completeness of the DEMO Specification Language (DEMOSL), the specification language that accompanies the DEMO method

Towards consistent demarcation of enterprise design domains

This article supports the ideology that enterprise engineering (EE) could add more value if EE researchers focus on facilitating effective conversations within design teams to create a common understanding of the enterprise. One way of creating a common understanding is to define and demarcate enterprise design domains in a consistent way. Literature presents different conceptualisations for demarcating design domains, without using a systematic demarcation rationale. As an example, this article introduces Hoogervorst’s approach and associated enterprise design domains to highlight practical difficulties when emerging design principles are applied to four main design domains, as defined by Hoogervorst. Based on the suggestion to apply the basic system design process to demarcate the main enterprise design domains in a consistent way and addressing the need for additional design domains, we present four alternative enterprise design domains, developed via design science research. We also demonstrate the usefulness of the new design domains by presenting several examples of enterprise design cycles that occur during enterprise design.http://link.springer.combookseries/5582018-11-10hj2018Industrial and Systems Engineerin